import os
## local Django settings for wjContact project. 
##
## This file contains settings that are unique to a local development machine, 
## such as paths to local template directories, and database connection 
## details. This file should never be put under version control!
##
##
## To use this file, first save a copy called 'local_settings.py' in the same 
## directory as the main settings.py file which you wish it to over-ride. Then
## put any settings variables which you wish to over-ride locally into this
## file. The values set here will over-ride those set in the main file.
## Do NOT add this file to version control! If you are getting annoying 
## messages from subversion all the time telling you that there is a file in 
## the directory which is not versioned or similar, you can add it to the 
## subversion 'ignore list'. In eclipse you can do this by right clicking on
## the filename in the project tree, and selecting 'team--> add to svn::ignore'
## However this will vary depending on what subversion and development software
## you are using. If you are having problems let me know :) 
 
## There is a very good manual for subversion at http://svnbook.red-bean.com/

## Likewise, if you have accidentally added it to version control it can be 
## removed using something like 'svn-delete' followed by 'svn-commit' at the 
## command line:
## 
##      $ svn delete myfile
##      D         myfile
##
##      $ svn commit -m "Deleted file 'myfile'."
##      Deleting       myfile
##      Transmitting file data .
##      Committed revision 14.
##
## You may also need a password and username. For more see 
## http://svnbook.red-bean.com/en/1.4/svn.ref.svn.c.delete.html
## Again, if you are having any problems let me or Jan know and We'll get it 
## sorted.

##  ------------->    IMPORTANT!!!  <-------------                          ####
## 
## 1. The actual version of this file should never be put under version control! (It is fine for the template which you are reading to be versioned though)
## If you wish to version a copy every now and 
## then,copy the contents into a seperate file with a different name 
## (ie wendy_local_settings.py) and version that one instead. Note: to stop a 
## file from being versioned by subversion, you can just never add it to 
## subversion in the first place. What you want to end up with is:
##
## a) A 'settings.py' file --. versioned in the subversion repository, containing
## settings which are relevant to everyone, and settings for final deployment
## 
## b) A 'local_settings.py' file which contains your unique local settings. This
## should never be added to the repository! The file you are reading now is a 
## template file showing you how to use this. This file needs to named 
## 'local_settings' for it all to work correctly (settings.py will look for a 
## file called 'local_settings.py' for the over-rides, so if you rename it it 
## won't get found.)
##
## c) Optionally, a copy of your local_settings file wih a unique name, such
## as 'wendy_local_settings.py'. This is really just a 'back-up', and will not 
## be used. However it can be safely added to the repository and versioned 
## without messing up anyone else. If you are experimenting with various 
## settings and want to keep an older versionb, you can copy your local_settings
## into this uniquely-named file before diong so,  and commit the uniquely 
## named file rathre than the 'local_settings' file itself. [Anyone who adds
##  their local_settings file directly to the repository will be punished most 
## harshly!]
## 
## 
## 2. This file is just a 'template', to give an example of how to create
## your own localised settings file. This file is for settings which are unique
## to your local machine, such as paths to template directories and 
## authentication details for the databse and thta kind of thing. I have
## included a sample of th most common things you are likely to want to 
## over-ride, but it is by no means exhastive. Also, you probably will not
## want to over-ride all of the variables in this example file. For those
## which you don'y want to over-ride, but may want to later, it is tempting to
## leave 'place-holders' for later use. However you mustn't do this - read 
## point 3. below!
## 
## 3. Only put variables in here that you actually want to over-ride. If you put
## a 'place-holder' such as "DATABASE_PORT=''" into this file, then that is the
## value which will be used, even if there is another value(such as '1234') in 
## the main file. In other words the values in here will ALWAYS over-ride those
## in the main settings.py file, so only put one in if that is what you want!
##


# 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'ado_mssql'.
DATABASE_ENGINE = 'sqlite3' 
# Or path to database file if using sqlite3.
DATABASE_NAME = 'sqlitedb'   
# Not used with sqlite3.         
DATABASE_USER = '' 
# Not used with sqlite3.          
DATABASE_PASSWORD = '' 

## <wsl>  Added these to work with the part of the load_data script which 
## creates the site.
SITE_NAME = "Jan's Site"
SITE_DOMAIN = "jan.com"


# Absolute path to the directory that holds media.
# Example: "/home/media/media.lawrence.com/"
MEDIA_ROOT = os.path.join( os.path.dirname(__file__))


# URL that handles the media served from MEDIA_ROOT.
# Example: "http://media.lawrence.com"
MEDIA_URL = '/sitemedia/'


TEMPLATE_DIRS = (
    # Put strings here, like "/home/html/django_templates" or "C:/www/django/templates".
    # Always use forward slashes, even on Windows.
    # Don't forget to use absolute paths, not relative paths.
    #"C:\Documents and Settings\wendy_admin\src\eclipse_workspace\djangodb\misc\wendy\wjContact\contacts\templates"  
	os.path.join( os.path.dirname(__file__), 'templates'),
	os.path.join( os.path.dirname(__file__), 'contacts/templates'),
	os.path.join( os.path.dirname(__file__), 'computers/templates'),
	os.path.join( os.path.dirname(__file__), 'sales/templates'),
)


ROOT_URLCONF = 'wjContact.urls'
